Module always opens with a filter, Why?

I have one module that opens up with a filter.
I turn off the filter, go into advanced settings, and remove the filter.
Then close the filter dialog.

I then go back into the filter dialog, and the "deleted" filter is still there.

How can I remove this?

Thanks for any insight into this issue.

DOORS 9_4
Gedinfo - Fri Sep 21 14:22:51 EDT 2012

Re: Module always opens with a filter, Why?
rmoskwa - Fri Sep 21 16:11:35 EDT 2012

The default view that you are using to open the module has a filter associated with it.

Re: Module always opens with a filter, Why?
Gedinfo - Fri Sep 21 16:13:07 EDT 2012

rmoskwa - Fri Sep 21 16:11:35 EDT 2012
The default view that you are using to open the module has a filter associated with it.

Other modules in the folder do not have this issue.

Re: Module always opens with a filter, Why?
rmoskwa - Fri Sep 21 16:14:59 EDT 2012

You need to remove the filter from the view, and perform a View->Save As to re-save the present view as the default view.

Re: Module always opens with a filter, Why?
Gedinfo - Fri Sep 21 16:51:58 EDT 2012

rmoskwa - Fri Sep 21 16:14:59 EDT 2012
You need to remove the filter from the view, and perform a View->Save As to re-save the present view as the default view.

If I try to save the "Access to this view" as either Public or Custom, I get this message:

CRCRD5429W: You do not have permission to modify the view eTest View.

Re: Module always opens with a filter, Why?
kbmurphy - Fri Sep 21 17:03:29 EDT 2012

Gedinfo - Fri Sep 21 16:51:58 EDT 2012
If I try to save the "Access to this view" as either Public or Custom, I get this message:

CRCRD5429W: You do not have permission to modify the view eTest View.

Read the error message. It tells you that you need to save the view with a different name.

Does your company offer any DOORS training? This is very basic stuff.

Re: Module always opens with a filter, Why?
llandale - Mon Sep 24 14:07:41 EDT 2012

The symptom has nothing to do with views; if you define a filter then you cannot remove all of them. Notice that when you delete the last one, the "apply" button is grey'd out.

Yes, that does seem rather odd.

I notice when you load a view that has no stored filter, then that WILL erase the "current" filter. Not sure what to think about that since I see no such "erase" command for filters (the "delete" is de-allocating the Filter handle)

-Louie

Re: Module always opens with a filter, Why?
llandale - Mon Sep 24 14:27:36 EDT 2012

You could define a new filter:
  • attribute "Created On" is greater than "1970-Jan-01".
Then it HAS a filter that does nothing when activated.

-Louie

Re: Module always opens with a filter, Why?
kbmurphy - Mon Sep 24 16:39:01 EDT 2012

llandale - Mon Sep 24 14:07:41 EDT 2012
The symptom has nothing to do with views; if you define a filter then you cannot remove all of them. Notice that when you delete the last one, the "apply" button is grey'd out.

Yes, that does seem rather odd.

I notice when you load a view that has no stored filter, then that WILL erase the "current" filter. Not sure what to think about that since I see no such "erase" command for filters (the "delete" is de-allocating the Filter handle)

-Louie

> llandale wrote:
> The symptom has nothing to do with views;

It has everything to do with views based on the OPs first message, and then his error message.

In the first message, the OP states that the module "opens" with a filter. The only way this is possible is that a default view that is not the Standard view is set, and this particular view has a filter associated.

In the follow up message, the OP states that when he tries to remove the filter and save the view, he gets an error stating that he doesn't have access to save the view. Again, this has everything to do with views.

> Yes, that does seem rather odd.

I agree and disagree, Louie. From a UI perspective it's odd behavior. But looking at how DOORS works it's not odd at all. A filter is either on or off, period. You turn the filter on, or turn it off. That's all you can do. So if a filter is on, and you turn it off, and then delete the filter (in the UI), what happens when you turn that filter back on? DOORS stores that filter so the filter button can be enabled and disabled. This, in turn, saves time for a user to not have to recreate a filter each time they turn off filtering.

I just don't want to lead the OP astray. The OP needs some basic (very basic) DOORS training, and he's spending time trying to do something that is very trivial--he just wants to save a view with no filter applied, yet he's convinced there's a problem when there is no problem at all.

Re: Module always opens with a filter, Why?
SystemAdmin - Mon Sep 24 20:21:50 EDT 2012

llandale - Mon Sep 24 14:07:41 EDT 2012
The symptom has nothing to do with views; if you define a filter then you cannot remove all of them. Notice that when you delete the last one, the "apply" button is grey'd out.

Yes, that does seem rather odd.

I notice when you load a view that has no stored filter, then that WILL erase the "current" filter. Not sure what to think about that since I see no such "erase" command for filters (the "delete" is de-allocating the Filter handle)

-Louie

Louie wrote - "....I notice when you load a view that has no stored filter, then that WILL erase the "current" filter...."

As far as I know, at least up to DOORS v9.2, the experience is that if the "Filter" property of a saved View is unchecked, then when when that view is loaded it will not wipe an existing active filter.

As I recall it, if a View is saved with the "Filter" property checked, I'm pretty sure that this actually stores 2 properties, the state of the Filter ON\OFF switch and whatever the current filter criteria is. Even if no filter criteria has been defined, it will still store this as a kind of null\no filter.

Now here's the quirk that can catch some users out - if a filter has been defined and activated (Filter switch is ON), and is then deactivated (Filter switch is OFF), then when you save the current View with the View "Filter" property enabled, it will not only store the state of the switch as being currently "OFF", but it will still also store the current filter criteria. So when you load that View later, the state of the Filter switch will be forced to OFF, which will effectively clear any existing filter, but if you toggle the Filter ON\OFF icon, it will activate the filter criteria that was saved with the View - and if that filter criteria at the time of saving the View was null, then that is exactly what is applied. This has raised eyebrows and tempers on a few occasions!!

Something that has caught users out is that the Filter ON\OFF switch does not re-apply a filter to the current display set - since about DOORS 8.2 I think, an icon was introduced that will re-apply the filter, but I still come across users who thought the Filter ON\OFF switch also re-applied the filter.

Paul Miller,
Melbourne, Australia

Re: Module always opens with a filter, Why?
llandale - Thu Sep 27 12:09:23 EDT 2012

SystemAdmin - Mon Sep 24 20:21:50 EDT 2012
Louie wrote - "....I notice when you load a view that has no stored filter, then that WILL erase the "current" filter...."

As far as I know, at least up to DOORS v9.2, the experience is that if the "Filter" property of a saved View is unchecked, then when when that view is loaded it will not wipe an existing active filter.

As I recall it, if a View is saved with the "Filter" property checked, I'm pretty sure that this actually stores 2 properties, the state of the Filter ON\OFF switch and whatever the current filter criteria is. Even if no filter criteria has been defined, it will still store this as a kind of null\no filter.

Now here's the quirk that can catch some users out - if a filter has been defined and activated (Filter switch is ON), and is then deactivated (Filter switch is OFF), then when you save the current View with the View "Filter" property enabled, it will not only store the state of the switch as being currently "OFF", but it will still also store the current filter criteria. So when you load that View later, the state of the Filter switch will be forced to OFF, which will effectively clear any existing filter, but if you toggle the Filter ON\OFF icon, it will activate the filter criteria that was saved with the View - and if that filter criteria at the time of saving the View was null, then that is exactly what is applied. This has raised eyebrows and tempers on a few occasions!!

Something that has caught users out is that the Filter ON\OFF switch does not re-apply a filter to the current display set - since about DOORS 8.2 I think, an icon was introduced that will re-apply the filter, but I still come across users who thought the Filter ON\OFF switch also re-applied the filter.

Paul Miller,
Melbourne, Australia

The key component of this thread is the inability to erase the filter; set it to "null". That fault has nothing to do with views; although the get-around does have to do with views.

I think it odd that you can turn a filter on or off but no convenient way to erase a filter. That's like being able to turn my blender on or off but no way to take it off the counter. An impossible reality my wife resolved yesterday but I digress...

Yes, I see now when you load a view which does not remember the filter, then the existing filter is preserved.

The only way I see to "erase" a filter is to load a view that does remember view settings, but there was no view defined at all when the view was saved. That is, the view remembers no-filter as opposed to a view that doesn't remember the filter. It appears the "Standard view" does remember such a null filter, and is the only original way to erase it.

So I see two hokey get-arounds.
  1. Remember your columns, load the Standard view, re-establish the columns, and save your filterless view
  2. Rememeber a BS filter that does nothing useful: such as "Attr 'Last Modified On' is greater than '1-Jan-1970'".

-Louie